Skip to content

[fix](test) fix case test_array_agg_view use same table in a database#59027

Merged
hello-stephen merged 1 commit intoapache:masterfrom
feiniaofeiafei:fix_case_test_array_agg_view
Dec 16, 2025
Merged

[fix](test) fix case test_array_agg_view use same table in a database#59027
hello-stephen merged 1 commit intoapache:masterfrom
feiniaofeiafei:fix_case_test_array_agg_view

Conversation

@feiniaofeiafei
Copy link
Contributor

@feiniaofeiafei feiniaofeiafei commented Dec 15, 2025

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #58031

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason

  • Behavior changed:

    • No.
    • Yes.

  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@feiniaofeiafei feiniaofeiafei force-pushed the fix_case_test_array_agg_view branch from 5551b7c to b903632 Compare December 15, 2025 03:19
@hello-stephen
Copy link
Contributor

hello-stephen commented Dec 15, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@feiniaofeiafei
Copy link
Contributor Author

feiniaofeiafei commented Dec 15, 2025

run buildall

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 15, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 15, 2025

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 15, 2025

PR approved by anyone and no changes requested.

@hello-stephen hello-stephen merged commit f2619bd into apache:master Dec 16, 2025
28 of 29 checks passed
github-actions bot pushed a commit that referenced this pull request Dec 16, 2025
@feiniaofeiafei
[fix](test) fix case test_array_agg_view use same table in a database (…
0fae966 
…#59027)

Related PR: #58031
@github-actions github-actions bot mentioned this pull request Dec 16, 2025
Merged
yiguolei pushed a commit that referenced this pull request Dec 19, 2025
@github-actions @feiniaofeiafei
branch-4.0: [fix](test) fix case test_array_agg_view use same table i…
4e06063 
…n a database #59027 (#59076)

Cherry-picked from #59027

Co-authored-by: feiniaofeiafei <moailing@selectdb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hello-stephen hello-stephen hello-stephen approved these changes

@morrySnow morrySnow morrySnow approved these changes

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. dev/4.0.3-merged reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@feiniaofeiafei @hello-stephen @morrySnow @yiguolei